Glossary: deprecate "Payload Body" per RFC 9110 #37598
Open
+3
−27
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The entry for "HTTP Content" now contains the details formerly described here. This rewrite makes this entry something of a historical record, which is useful since people will likely be using the word "payload" in its former context for many years.
github-actions
bot
added
Content:Glossary
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
Preview URLs External URLs (3)URL:
(comment last updated: 2025-01-13 10:56:36) |
The bot changed my double spaces to single spaces after periods. That's fine. Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
The bot turned my absolute link into a relative link. I should have done that myself. Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
estelle
changed the title
bsmth
reviewed
Jan 14, 2025
| ``` | ||
|
|
||
| For more information see [RFC 7230, section 3.3: Message Body](https://datatracker.ietf.org/doc/html/rfc7230#section-3.3) and [RFC 7230, section 3.3.1: Transfer-Encoding](https://datatracker.ietf.org/doc/html/rfc7230#section-3.3.1). | ||
| For more information see [RFC 7230, section 3.3: Message Body](https://datatracker.ietf.org/doc/html/rfc7230#section-3.3), [RFC 7231, section 3: Representations](https://datatracker.ietf.org/doc/html/rfc7231#section-3), and [RFC 9110, appendix B.3: Changes from RFC 7231](https://datatracker.ietf.org/doc/html/rfc9110#name-changes-from-rfc-7231). |
There was a problem hiding this comment.
Let's use a See also section like the other entry:
Suggested change
| For more information see [RFC 7230, section 3.3: Message Body](https://datatracker.ietf.org/doc/html/rfc7230#section-3.3), [RFC 7231, section 3: Representations](https://datatracker.ietf.org/doc/html/rfc7231#section-3), and [RFC 9110, appendix B.3: Changes from RFC 7231](https://datatracker.ietf.org/doc/html/rfc9110#name-changes-from-rfc-7231). | |
| ## See also | |
| - {{Glossary("Content header")}} | |
| - [RFC 9110, section 6.4: Content](https://httpwg.org/specs/rfc9110.html#rfc.section.6.4) (obsoletes [RFC 7231](https://datatracker.ietf.org/doc/html/rfc7231#section-3.3) Payload Semantics) | |
| - [Changes from RFC 7231](https://httpwg.org/specs/rfc9110.html#changes.from.rfc.7231) |
bsmth
reviewed
Jan 14, 2025
| @@ -6,32 +6,8 @@ page-type: glossary-definition | |||
|
|
|||
| {{GlossarySidebar}} | |||
|
|
|||
| The HTTP message **payload body** is the _information_ ("payload") part of the data that is sent in the HTTP Message Body (if any), prior to [transfer encoding](/en-US/docs/Web/HTTP/Headers/Transfer-Encoding) being applied. If transfer encoding is not used, the _payload body_ and _message body_ are the same! | |||
| Prior to June 2022, the **payload body** or **payload** was the resource representation being transferred in an HTTP Message Body, stripped of any [transfer encoding](/en-US/docs/Web/HTTP/Headers/Transfer-Encoding). With no transfer encoding, the _payload body_ and _message body_ are the same thing. Representation data could also be transferred in the HTTP Header, but such data would not be regarded as "payload". | |||
There was a problem hiding this comment.
Suggested change
| Prior to June 2022, the **payload body** or **payload** was the resource representation being transferred in an HTTP Message Body, stripped of any [transfer encoding](/en-US/docs/Web/HTTP/Headers/Transfer-Encoding). With no transfer encoding, the _payload body_ and _message body_ are the same thing. Representation data could also be transferred in the HTTP Header, but such data would not be regarded as "payload". | |
| Prior to June 2022, the **payload body** or **payload** was the resource representation transferred in an HTTP message body, stripped of any [transfer encoding](/en-US/docs/Web/HTTP/Headers/Transfer-Encoding). With no transfer encoding, the _payload body_ and _message body_ are the same thing. Representation data could also be transferred in HTTP headers, but such data would not be regarded as a "payload". |
|
Thanks @crossaw - a couple of suggestions for you above! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The entry for "HTTP Content" now contains the details formerly described here. This rewrite makes this entry something of a historical record, which is useful since people will likely be using the word "payload" in its former context for many years.
Description
Motivation
Additional details
Related issues and pull requests